Voice-controlled settings and navigation

ABSTRACT

A system and method for controlling an electronic eyewear device using voice commands receives audio data from a microphone, processes the audio data to identify a wake word, and upon identification of a wake word, processes the audio data to identify at least one action keyword in the audio data. The audio data is provided to one of a plurality of controllers associated with different action keywords or sets of action keywords to implement an action. For example, the audio data may be provided to a settings controller to adjust settings of the electronic eyewear device when the action keyword is indicative of a request to adjust a setting of the electronic eyewear device or to a navigation controller to navigate to the system information of the electronic eyewear device when the action keyword is indicative of a request to navigate to system information of the electronic eyewear device.

TECHNICAL FIELD

Examples set forth in the present disclosure relate to a voice interfacefor portable electronic devices, including wearable electronic devicessuch as augmented reality (a.k.a., smart) glasses. More particularly,but not by way of limitation, the present disclosure describestechniques for adjusting settings and navigating in response to voiceinputs to an electronic eyewear device.

BACKGROUND

Wearable electronic devices such as electronic eyewear devices maycommunicate with application programs running on mobile devices such asa user's smartphone and, in some cases, may communicate directly with aserver. In either case, the electronic eyewear device may support directdevice integration with communication application backend services aswell as third-party application programming interfaces (APIs) such astext-to-speech, the SHAZAM PLAYER® app, and the like. The wearer of theelectronic eyewear devices may select display features throughinteraction with the electronic eyewear device. The limited interfacesto the electronic eyewear device make selection of display features andsettings difficult.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the various implementations disclosed will be readilyunderstood from the following detailed description, in which referenceis made to the appended drawing figures. A reference numeral is usedwith each element in the description and throughout the several views ofthe drawings. When a plurality of similar elements is present, a singlereference numeral may be assigned to like elements, with an addedlower-case letter referring to a specific element.

The various elements shown in the figures are not drawn to scale unlessotherwise indicated. The dimensions of the various elements may beenlarged or reduced in the interest of clarity. The several figuresdepict one or more implementations and are presented by way of exampleonly and should not be construed as limiting. Included in the drawingsare the following figures:

FIG. 1A illustrates a side view of an example hardware configuration ofan electronic eyewear device showing a right optical assembly with animage display;

FIG. 1B illustrates a top cross-sectional view of a temple of theelectronic eyewear device of FIG. 1A;

FIG. 2A illustrates a rear view of an example hardware configuration ofan electronic eyewear device in an example hardware configuration;

FIG. 2B illustrates a rear view of an example hardware configuration ofanother electronic eyewear device in an example hardware configuration;

FIG. 2C and FIG. 2D illustrate rear views of example hardwareconfigurations of an electronic eyewear device including two differenttypes of image displays;

FIG. 3 illustrates a rear perspective view of the electronic eyeweardevice of FIG. 2A depicting an infrared emitter, an infrared camera, aframe front, a frame back, and a circuit board;

FIG. 4 illustrates a cross-sectional view taken through the infraredemitter and the frame of the electronic eyewear device of FIG. 3 ;

FIG. 5 illustrates an example of visible light captured by the leftvisible light camera as a left raw image and visible light captured bythe right visible light camera as a right raw image;

FIG. 6 illustrates a block diagram of electronic components of theelectronic eyewear device;

FIG. 7 illustrates a voice scan architecture where a scan intent handlerdetermines the user's intent based on at least one of a wake word or eyescan intent data;

FIG. 8 illustrates a generalized voice command system including a voiceactions service having a voice command intent handler that performs theinitial interpretation of the voice command and routes it to theappropriate controller depending on its nature;

FIG. 9 illustrates a sample flow chart of the dispatch function of thevoice actions service in a sample configuration;

FIGS. 10A-10D illustrate sample user interfaces for what would bepresented to each eye in a sample configuration: FIG. 10A illustratesthe user interface before an application has been selected; FIG. 10Billustrates the user interface when the user has asked to see the volumelevel; FIG. 10C illustrates the user interface when the user has askedto increase the volume by 10%; and FIG. 10D illustrates the userinterface when the user has asked to see the brightness level; and

FIG. 11 illustrates a sample configuration of a computer system adaptedto implement at least one of the server and the device hub in accordancewith the systems and methods described herein.

DETAILED DESCRIPTION

When using a portable electronic device such as augmented reality(a.k.a., smart) glasses, conventional devices often make it difficult toread and change settings (e.g., brightness, volume, WI-FI® connectivity,battery level, thermal status, etc.) and to navigate to the systeminformation or applications. For viewing most settings, the user isrequired to navigate to system information, which is not very convenientfor a quick battery or temperature level check. Changing settings mayrequire access to a paired device even in the case of simple brightnessadjustments. It is desired to provide systems and methods for readingand changing settings and to navigate to the system information usingsimple voice commands without requiring access to a paired device.

The systems and methods described herein expand the use of a wake wordvoice command such as “Hey Snapchat . . . ” beyond voice scanning toprovide infrastructure for general purpose voice commands (not just forsettings). To facilitate settings adjustments, commands such as thefollowing may be recognized: “volume/brightness up [+10],”“volume/brightness down [−10],” “set brightness/volume to n %,” “providebrightness setting,” “provide battery level,” “provide temperature,”etc. However, the range can be extended to support virtually anywell-defined voice command. The response to the command may becommunicated as a notification/alert using, for example, an intent-basedinfrastructure.

In a sample configuration, the user may propose augmented reality (AR)device settings adjustments and preview the adjustments on-the-go, inany context, without the need to access a paired device. The systems andmethods described herein support almost arbitrary voice and navigationcommands like “set brightness to 10%,” “what's my battery level,” or “goto gallery.” Such a voice controlled interface is especially importantfor personal electronic devices such as AR glasses as there typically isno touch input or keyboard. The alternative is to go to the pairedcompanion app on an associated smartphone to adjust the settings. Suchan approach is very inconvenient. The voice interface described hereinrenders such navigation for settings adjustment unnecessary.

This disclosure is thus directed to a system, a method, andcomputer-readable medium including instructions for controlling anelectronic eyewear device using voice commands. The system and methodare adapted to receive audio data from a microphone, process the audiodata to identify a wake word, and process the audio data to identify atleast one action keyword in the audio data. Upon identification of thewake word, the audio data is provided to one of a plurality ofcontrollers associated with different action keywords or sets of actionkeywords to implement an action. For example, the audio data may beprovided to a settings controller to adjust settings of the electroniceyewear device when the action keyword is indicative of a request toadjust a setting of the electronic eyewear device or to a navigationcontroller to navigate to the system information of the electroniceyewear device when the action keyword is indicative of a request tonavigate to system information of the electronic eyewear device. Whenthe audio data does not contain an action keyword indicative of arequest to adjust a setting of the electronic eyewear device or of arequest to navigate to system information of the electronic eyeweardevice, the audio data may be provided to a scan controller. At leastone of results of an action requested by the action keyword or set ofaction keywords or a notification indicating an action taken in responseto the audio data received at the microphone may be provided to thedisplay without disrupting a current action being presented to thedisplay as part of execution of a software application.

The following detailed description includes systems, methods,techniques, instruction sequences, and computer program productsillustrative of examples set forth in the disclosure. Numerous detailsand examples are included for the purpose of providing a thoroughunderstanding of the disclosed subject matter and its relevantteachings. Those skilled in the relevant art, however, may understandhow to apply the relevant teachings without such details. Aspects of thedisclosed subject matter are not limited to the specific devices,systems, and methods described because the relevant teachings can beapplied or practiced in a variety of ways. The terminology andnomenclature used herein is for the purpose of describing particularaspects only and is not intended to be limiting. In general, well-knowninstruction instances, protocols, structures, and techniques are notnecessarily shown in detail.

The term “connect,” “connected,” “couple,” and “coupled” as used hereinrefers to any logical, optical, physical, or electrical connection,including a link or the like by which the electrical or magnetic signalsproduced or supplied by one system element are imparted to anothercoupled or connected system element. Unless described otherwise,coupled, or connected elements or devices are not necessarily directlyconnected to one another and may be separated by intermediatecomponents, elements, or communication media, one or more of which maymodify, manipulate, or carry the electrical signals. The term “on” meansdirectly supported by an element or indirectly supported by the elementthrough another element integrated into or supported by the element.

Additional objects, advantages and novel features of the examples willbe set forth in part in the following description, and in part willbecome apparent to those skilled in the art upon examination of thefollowing and the accompanying drawings or may be learned by productionor operation of the examples. The objects and advantages of the presentsubject matter may be realized and attained by means of themethodologies, instrumentalities and combinations particularly pointedout in the appended claims.

The orientations of the electronic eyewear device, associated componentsand any complete devices incorporating an eye scanner and camera such asshown in any of the drawings, are given by way of example only, forillustration and discussion purposes. In operation for a particularvariable optical processing application, the electronic eyewear devicemay be oriented in any other direction suitable to the particularapplication of the electronic eyewear device, for example up, down,sideways, or any other orientation. Also, to the extent used herein, anydirectional term, such as front, rear, inwards, outwards, towards, left,right, lateral, longitudinal, up, down, upper, lower, top, bottom andside, are used by way of example only, and are not limiting as todirection or orientation of any optic or component of an opticconstructed as otherwise described herein.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below. A sample electronic eyeweardevice with a voice interface will be described with respect to FIGS.1-11 .

FIG. 1A illustrates a side view of an example hardware configuration ofan electronic eyewear device 100 including a right optical assembly 180Bwith an image display 180D (FIG. 2A). Electronic eyewear device 100includes multiple visible light cameras 114A-B (FIG. 5 ) that form astereo camera, of which the right visible light camera 114B is locatedon a right temple 110B and the left visible light camera 114A is locatedon a left temple 110A.

The left and right visible light cameras 114A-B may include an imagesensor that is sensitive to the visible light range wavelength. Each ofthe visible light cameras 114A-B has a different frontward facing angleof coverage, for example, visible light camera 114B has the depictedangle of coverage 111B. The angle of coverage is an angle range in whichthe image sensor of the visible light camera 114A-B picks upelectromagnetic radiation and generates images. Examples of such visiblelights camera 114A-B include a high-resolution complementarymetal-oxide-semiconductor (CMOS) image sensor and a video graphic array(VGA) camera, such as 640p (e.g., 640×480 pixels for a total of 0.3megapixels), 720p, or 1080p. Image sensor data from the visible lightcameras 114A-B may be captured along with geolocation data, digitized byan image processor, and stored in a memory.

To provide stereoscopic vision, visible light cameras 114A-B may becoupled to an image processor (element 612 of FIG. 6 ) for digitalprocessing along with a timestamp in which the image of the scene iscaptured. Image processor 612 may include circuitry to receive signalsfrom the visible light camera 114A-B and to process those signals fromthe visible light cameras 114A-B into a format suitable for storage inthe memory (element 634 of FIG. 6 ). The timestamp may be added by theimage processor 612 or other processor that controls operation of thevisible light cameras 114A-B. Visible light cameras 114A-B allow thestereo camera to simulate human binocular vision. Stereo cameras alsoprovide the ability to reproduce three-dimensional images (image 515 ofFIG. 5 ) based on two captured images (elements 558A-B of FIG. 5 ) fromthe visible light cameras 114A-B, respectively, having the sametimestamp. Such three-dimensional images 515 allow for an immersivelife-like experience, e.g., for virtual reality or video gaming. Forstereoscopic vision, the pair of images 558A-B may be generated at agiven moment in time—one image for each of the left and right visiblelight cameras 114A-B. When the pair of generated images 558A-B from thefrontward facing field of view (FOV) 111A-B of the left and rightvisible light cameras 114A-B are stitched together (e.g., by the imageprocessor 612), depth perception is provided by the optical assembly180A-B.

In an example, the electronic eyewear device 100 includes a frame 105, aright rim 107B, a right temple 110B extending from a right lateral side170B of the frame 105, and a see-through image display 180D (FIGS. 2A-B)comprising optical assembly 180B to present a graphical user interfaceto a user. The electronic eyewear device 100 includes the left visiblelight camera 114A connected to the frame 105 or the left temple 110A tocapture a first image of the scene. Electronic eyewear device 100further includes the right visible light camera 114B connected to theframe 105 or the right temple 110B to capture (e.g., simultaneously withthe left visible light camera 114A) a second image of the scene whichpartially overlaps the first image. Although not shown in FIGS. 1A-B, aprocessor 632 (FIG. 6 ) is coupled to the electronic eyewear device 100and connected to the visible light cameras 114A-B and memory 634 (FIG. 6) accessible to the processor 632, and programming in the memory 634 maybe provided in the electronic eyewear device 100 itself.

Although not shown in FIG. 1A, the electronic eyewear device 100 alsomay include a head movement tracker (element 109 of FIG. 1B) or an eyemovement tracker (element 113 of FIG. 2A or element 213 of FIGS. 2B-C).Electronic eyewear device 100 may further include the see-through imagedisplays 180C-D of optical assembly 180A-B, respectfully, for presentinga sequence of displayed images, and an image display driver (element 642of FIG. 6 ) coupled to the see-through image displays 180C-D of opticalassembly 180A-B to control the image displays 180C-D of optical assembly180A-B to present the sequence of displayed images 515, which aredescribed in further detail below. Electronic eyewear device 100 mayfurther include the memory 634 and the processor 632 having access tothe image display driver 642 and the memory 634, as well as programmingin the memory 634. Execution of the programming by the processor 632configures the electronic eyewear device 100 to perform functions,including functions to present, via the see-through image displays180C-D, an initial displayed image of the sequence of displayed images,the initial displayed image having an initial field of viewcorresponding to an initial head direction or an initial eye gazedirection.

Execution of the programming by the processor 632 may further configurethe electronic eyewear device 100 to detect movement of a user of theelectronic eyewear device 100 by: (i) tracking, via the head movementtracker (element 109 of FIG. 1B), a head movement of a head of the user,or (ii) tracking, via an eye movement tracker (element 113 of FIG. 2A orelement 213 of FIGS. 2B-C), an eye movement of an eye of the user of theelectronic eyewear device 100. Execution of the programming by theprocessor 632 may further configure the electronic eyewear device 100 todetermine a field of view adjustment to the initial field of view of theinitial displayed image based on the detected movement of the user. Thefield of view adjustment may include a successive field of viewcorresponding to a successive head direction or a successive eyedirection. Execution of the programming by the processor 632 may furtherconfigure the electronic eyewear device 100 to generate a successivedisplayed image of the sequence of displayed images based on the fieldof view adjustment. Execution of the programming by the processor 632may further configure the electronic eyewear device 100 to present, viathe see-through image displays 180C-D of the optical assembly 180A-B,the successive displayed images.

FIG. 1B illustrates a top cross-sectional view of the temple of theelectronic eyewear device 100 of FIG. 1A depicting the right visiblelight camera 114B, a head movement tracker 109, and a circuit board 140.Construction and placement of the left visible light camera 114A issubstantially similar to the right visible light camera 114B, except theconnections and coupling are on the left lateral side 170A (FIG. 2A). Asshown, the electronic eyewear device 100 includes the right visiblelight camera 114B and a circuit board, which may be a flexible printedcircuit board (PCB) 140. The right hinge 126B connects the right temple110B to hinged arm 125B of the electronic eyewear device 100. In someexamples, components of the right visible light camera 114B, theflexible PCB 140, or other electrical connectors or contacts may belocated on the right temple 110B or the right hinge 126B.

As shown, electronic eyewear device 100 may include a head movementtracker 109, which includes, for example, an inertial measurement unit(IMU). An inertial measurement unit is an electronic device thatmeasures and reports a body's specific force, angular rate, andsometimes the magnetic field surrounding the body, using a combinationof accelerometers and gyroscopes, sometimes also magnetometers. Theinertial measurement unit works by detecting linear acceleration usingone or more accelerometers and rotational rate using one or moregyroscopes. Typical configurations of inertial measurement units containone accelerometer, gyro, and magnetometer per axis for each of the threeaxes: horizontal axis for left-right movement (X), vertical axis (Y) fortop-bottom movement, and depth or distance axis for up-down movement(Z). The accelerometer detects the gravity vector. The magnetometerdefines the rotation in the magnetic field (e.g., facing south, north,etc.) like a compass that generates a heading reference. The threeaccelerometers detect acceleration along the horizontal, vertical, anddepth axis defined above, which can be defined relative to the ground,the electronic eyewear device 100, or the user wearing the electroniceyewear device 100.

Electronic eyewear device 100 may detect movement of the user of theelectronic eyewear device 100 by tracking, via the head movement tracker109, the head movement of the head of the user. The head movementincludes a variation of head direction on a horizontal axis, a verticalaxis, or a combination thereof from the initial head direction duringpresentation of the initial displayed image on the image display. In oneexample, tracking, via the head movement tracker 109, the head movementof the head of the user includes measuring, via the inertial measurementunit 109, the initial head direction on the horizontal axis (e.g., Xaxis), the vertical axis (e.g., Y axis), or the combination thereof(e.g., transverse or diagonal movement). Tracking, via the head movementtracker 109, the head movement of the head of the user further includesmeasuring, via an inertial measurement unit of the head movement tracker109, a successive head direction on the horizontal axis, the verticalaxis, or the combination thereof during presentation of the initialdisplayed image.

Tracking, via the head movement tracker 109, the head movement of thehead of the user may further include determining the variation of headdirection based on both the initial head direction and the successivehead direction. Detecting movement of the user of the electronic eyeweardevice 100 may further include in response to tracking, via the headmovement tracker 109, the head movement of the head of the user,determining that the variation of head direction exceeds a deviationangle threshold on the horizontal axis, the vertical axis, or thecombination thereof. In sample configurations, the deviation anglethreshold is between about 3° to 10°. As used herein, the term “about”when referring to an angle means±10% from the stated amount.

Variation along the horizontal axis slides three-dimensional objects,such as characters, Bitmojis, application icons, etc. in and out of thefield of view by, for example, hiding, unhiding, or otherwise adjustingvisibility of the three-dimensional object. Variation along the verticalaxis, for example, when the user looks upwards, in one example, displaysweather information, time of day, date, calendar appointments, etc. Inanother example, when the user looks downwards on the vertical axis, theelectronic eyewear device 100 may power down.

As shown in FIG. 1B, the right temple 110B includes temple body 211 anda temple cap, with the temple cap omitted in the cross-section of FIG.1B. Disposed inside the right temple 110B are various interconnectedcircuit boards, such as PCBs or flexible PCBs 140, that includecontroller circuits for right visible light camera 114B, microphone(s)130, speaker(s) 132, low-power wireless circuitry (e.g., for wirelessshort-range network communication via BLUETOOTH®), and high-speedwireless circuitry (e.g., for wireless local area network communicationvia WI-FI®).

The right visible light camera 114B is coupled to or disposed on theflexible PCB 140 and covered by a visible light camera cover lens, whichis aimed through opening(s) formed in the right temple 110B. In someexamples, the frame 105 connected to the right temple 110B includes theopening(s) for the visible light camera cover lens. The frame 105 mayinclude a front-facing side configured to face outwards away from theeye of the user. The opening for the visible light camera cover lens maybe formed on and through the front-facing side. In the example, theright visible light camera 114B has an outward facing angle of coverage111B with a line of sight or perspective of the right eye of the user ofthe electronic eyewear device 100. The visible light camera cover lensalso can be adhered to an outward facing surface of the right temple110B in which an opening is formed with an outwards facing angle ofcoverage, but in a different outwards direction. The coupling can alsobe indirect via intervening components.

Left (first) visible light camera 114A may be connected to the leftsee-through image display 180C of left optical assembly 180A to generatea first background scene of a first successive displayed image. Theright (second) visible light camera 114B may be connected to the rightsee-through image display 180D of right optical assembly 180B togenerate a second background scene of a second successive displayedimage. The first background scene and the second background scene maypartially overlap to present a three-dimensional observable area of thesuccessive displayed image.

Flexible PCB 140 may be disposed inside the right temple 110B andcoupled to one or more other components housed in the right temple 110B.Although shown as being formed on the circuit boards 140 of the righttemple 110B, the right visible light camera 114B can be formed on thecircuit boards 140 of the left temple 110A, the hinged arms 125A-B, orframe 105.

FIG. 2A illustrates a rear view of an example hardware configuration ofan electronic eyewear device 100. As shown in FIG. 2A, the electroniceyewear device 100 is in a form configured for wearing by a user, whichare eyeglasses in the example of FIG. 2A. The electronic eyewear device100 can take other forms and may incorporate other types of frameworks,for example, a headgear, a headset, or a helmet.

In the eyeglasses example, electronic eyewear device 100 includes theframe 105 which includes the left rim 107A connected to the right rim107B via the bridge 106 adapted for a nose of the user. The left andright rims 107A-B include respective apertures 175A-B which hold therespective optical element 180A-B, such as a lens and the see-throughdisplays 180C-D. As used herein, the term lens is meant to covertransparent or translucent pieces of glass or plastic having curved andflat surfaces that cause light to converge/diverge or that cause littleor no convergence/divergence.

Although shown as having two optical elements 180A-B, the electroniceyewear device 100 can include other arrangements, such as a singleoptical element depending on the application or intended user of theelectronic eyewear device 100. As further shown, electronic eyeweardevice 100 includes the left temple 110A adjacent the left lateral side170A of the frame 105 and the right temple 110B adjacent the rightlateral side 170B of the frame 105. The temples 110A-B may be integratedinto the frame 105 on the respective sides 170A-B (as illustrated) orimplemented as separate components attached to the frame 105 on therespective sides 170A-B. Alternatively, the temples 110A-B may beintegrated into hinged arms 125A-B attached to the frame 105.

In the example of FIG. 2A, an eye scanner 113 may be provided thatincludes an infrared emitter 115 and an infrared camera 120. Visiblelight cameras typically include a blue light filter to block infraredlight detection. In an example, the infrared camera 120 is a visiblelight camera, such as a low-resolution video graphic array (VGA) camera(e.g., 640×480 pixels for a total of 0.3 megapixels), with the bluefilter removed. The infrared emitter 115 and the infrared camera 120 maybe co-located on the frame 105. For example, both are shown as connectedto the upper portion of the left rim 107A. The frame 105 or one or moreof the left and right temples 110A-B may include a circuit board (notshown) that includes the infrared emitter 115 and the infrared camera120. The infrared emitter 115 and the infrared camera 120 can beconnected to the circuit board by soldering, for example.

Other arrangements of the infrared emitter 115 and infrared camera 120may be implemented, including arrangements in which the infrared emitter115 and infrared camera 120 are both on the right rim 107B, or indifferent locations on the frame 105. For example, the infrared emitter115 may be on the left rim 107A and the infrared camera 120 may be onthe right rim 107B. In another example, the infrared emitter 115 may beon the frame 105 and the infrared camera 120 may be on one of thetemples 110A-B, or vice versa. The infrared emitter 115 can be connectedessentially anywhere on the frame 105, left temple 110A, or right temple110B to emit a pattern of infrared light. Similarly, the infrared camera120 can be connected essentially anywhere on the frame 105, left temple110A, or right temple 110B to capture at least one reflection variationin the emitted pattern of infrared light.

The infrared emitter 115 and infrared camera 120 may be arranged to faceinwards towards an eye of the user with a partial or full field of viewof the eye in order to identify the respective eye position and gazedirection. For example, the infrared emitter 115 and infrared camera 120may be positioned directly in front of the eye, in the upper part of theframe 105 or in the temples 110A-B at either ends of the frame 105.

FIG. 2B illustrates a rear view of an example hardware configuration ofanother electronic eyewear device 200. In this example configuration,the electronic eyewear device 200 is depicted as including an eyescanner 213 on a right temple 210B. As shown, an infrared emitter 215and an infrared camera 220 are co-located on the right temple 210B. Itshould be understood that the eye scanner 213 or one or more componentsof the eye scanner 213 can be located on the left temple 210A and otherlocations of the electronic eyewear device 200, for example, the frame105. The infrared emitter 215 and infrared camera 220 are like that ofFIG. 2A, but the eye scanner 213 can be varied to be sensitive todifferent light wavelengths as described previously in FIG. 2A. Similarto FIG. 2A, the electronic eyewear device 200 includes a frame 105 whichincludes a left rim 107A which is connected to a right rim 107B via abridge 106. The left and right rims 107A-B may include respectiveapertures which hold the respective optical elements 180A-B comprisingthe see-through display 180C-D.

FIGS. 2C-D illustrate rear views of example hardware configurations ofthe electronic eyewear device 100, including two different types ofsee-through image displays 180C-D. In one example, these see-throughimage displays 180C-D of optical assembly 180A-B include an integratedimage display. As shown in FIG. 2C, the optical assemblies 180A-Binclude a suitable display matrix 180C-D of any suitable type, such as aliquid crystal display (LCD), an organic light-emitting diode (OLED)display, a waveguide display, or any other such display.

The optical assembly 180A-B also includes an optical layer or layers176, which can include lenses, optical coatings, prisms, mirrors,waveguides, optical strips, and other optical components in anycombination. The optical layers 176A-N can include a prism having asuitable size and configuration and including a first surface forreceiving light from display matrix and a second surface for emittinglight to the eye of the user. The prism of the optical layers 176A-N mayextend over all or at least a portion of the respective apertures 175A-Bformed in the left and right rims 107A-B to permit the user to see thesecond surface of the prism when the eye of the user is viewing throughthe corresponding left and right rims 107A-B. The first surface of theprism of the optical layers 176A-N faces upwardly from the frame 105 andthe display matrix overlies the prism so that photons and light emittedby the display matrix impinge the first surface. The prism may be sizedand shaped so that the light is refracted within the prism and isdirected towards the eye of the user by the second surface of the prismof the optical layers 176A-N. In this regard, the second surface of theprism of the optical layers 176A-N can be convex to direct the lighttowards the center of the eye. The prism can optionally be sized andshaped to magnify the image projected by the see-through image displays180C-D, and the light travels through the prism so that the image viewedfrom the second surface is larger in one or more dimensions than theimage emitted from the see-through image displays 180C-D.

In another example, the see-through image displays 180C-D of opticalassembly 180A-B may include a projection image display as shown in FIG.2D. The optical assembly 180A-B includes a projector 150, which may be athree-color projector using a scanning mirror, a galvanometer, a laserprojector, or other types of projectors. During operation, an opticalsource such as a projector 150 is disposed in or on one of the temples110A-B of the electronic eyewear device 100. Optical assembly 180-B mayinclude one or more optical strips 155A-N spaced apart across the widthof the lens of the optical assembly 180A-B or across a depth of the lensbetween the front surface and the rear surface of the lens.

As the photons projected by the projector 150 travel across the lens ofthe optical assembly 180A-B, the photons encounter the optical strips155A-N. When a particular photon encounters a particular optical strip,the photon is either redirected towards the user's eye, or it passes tothe next optical strip. A combination of modulation of projector 150,and modulation of optical strips, may control specific photons or beamsof light. In an example, a processor controls optical strips 155A-N byinitiating mechanical, acoustic, or electromagnetic signals. Althoughshown as having two optical assemblies 180A-B, the electronic eyeweardevice 100 can include other arrangements, such as a single or threeoptical assemblies, or the optical assembly 180A-B may have arrangeddifferent arrangement depending on the application or intended user ofthe electronic eyewear device 100.

As further shown in FIGS. 2C-D, electronic eyewear device 100 includes aleft temple 110A adjacent the left lateral side 170A of the frame 105and a right temple 110B adjacent the right lateral side 170B of theframe 105. The temples 110A-B may be integrated into the frame 105 onthe respective lateral sides 170A-B (as illustrated) or implemented asseparate components attached to the frame 105 on the respective sides170A-B. Alternatively, the temples 110A-B may be integrated into thehinged arms 125A-B attached to the frame 105.

In one example, the see-through image displays include the firstsee-through image display 180C and the second see-through image display180D. Electronic eyewear device 100 may include first and secondapertures 175A-B that hold the respective first and second opticalassembly 180A-B. The first optical assembly 180A may include the firstsee-through image display 180C (e.g., a display matrix of FIG. 2C oroptical strips 155A-N′ and a projector 150A (not shown) in left temple110A). The second optical assembly 180B may include the secondsee-through image display 180D (e.g., a display matrix of FIG. 2C oroptical strips 155A-N″ and a projector 150B (not shown) in right temple110B). The successive field of view of the successive displayed imagemay include an angle of view between about 15° to 30°, and morespecifically 24°, measured horizontally, vertically, or diagonally. Thesuccessive displayed image having the successive field of viewrepresents a combined three-dimensional observable area visible throughstitching together of two displayed images presented on the first andsecond image displays.

As used herein, “an angle of view” describes the angular extent of thefield of view associated with the displayed images presented on each ofthe left and right image displays 180C-D of optical assembly 180A-B. The“angle of coverage” describes the angle range that a lens of visiblelight cameras 114A-B or infrared camera 220 can image. Typically, theimage circle produced by a lens is large enough to cover the film orsensor completely, possibly including some vignetting (i.e., a reductionof an image's brightness or saturation toward the periphery compared tothe image center). If the angle of coverage of the lens does not fillthe sensor, the image circle will be visible, typically with strongvignetting toward the edge, and the effective angle of view will belimited to the angle of coverage. The “field of view” is intended todescribe the field of observable area which the user of the electroniceyewear device 100 can see through his or her eyes via the displayedimages presented on the left and right image displays 180C-D of theoptical assembly 180A-B. Image display 180C of optical assembly 180A-Bcan have a field of view with an angle of coverage between 15° to 30°,for example 24°, and have a resolution of 480×480 pixels.

FIG. 3 illustrates a rear perspective view of the electronic eyeweardevice 100 of FIG. 2A. The electronic eyewear device 100 includes aninfrared emitter 215, infrared camera 220, a frame front 330, a frameback 335, and a circuit board 340. It can be seen in FIG. 3 that theupper portion of the left rim of the frame of the electronic eyeweardevice 100 may include the frame front 330 and the frame back 335. Anopening for the infrared emitter 215 is formed on the frame back 335.

As shown in the encircled cross-section 4 in the upper middle portion ofthe left rim of the frame, a circuit board, which may be a flexible PCB340, is sandwiched between the frame front 330 and the frame back 335.Also shown in further detail is the attachment of the left temple 110Ato the left hinged arm 325A via the left hinge 126A. In some examples,components of the eye movement tracker 213, including the infraredemitter 215, the flexible PCB 340, or other electrical connectors orcontacts may be located on the left hinged arm 325A or the left hinge126A.

FIG. 4 is a cross-sectional view through the infrared emitter 215 andthe frame corresponding to the encircled cross-section 4 of theelectronic eyewear device 100 of FIG. 3 . Multiple layers of theelectronic eyewear device 100 are illustrated in the cross-section ofFIG. 4 . As shown, the frame includes the frame front 330 and the frameback 335. The flexible PCB 340 is disposed on the frame front 330 andconnected to the frame back 335. The infrared emitter 215 is disposed onthe flexible PCB 340 and covered by an infrared emitter cover lens 445.For example, the infrared emitter 215 may be reflowed to the back of theflexible PCB 340. Reflowing attaches the infrared emitter 215 to contactpad(s) formed on the back of the flexible PCB 340 by subjecting theflexible PCB 340 to controlled heat which melts a solder paste toconnect the two components. In one example, reflowing is used to surfacemount the infrared emitter 215 on the flexible PCB 340 and electricallyconnect the two components. However, it should be understood thatthrough-holes can be used to connect leads from the infrared emitter 215to the flexible PCB 340 via interconnects, for example.

The frame back 335 may include an infrared emitter opening 450 for theinfrared emitter cover lens 445. The infrared emitter opening 450 isformed on a rear-facing side of the frame back 335 that is configured toface inwards towards the eye of the user. In the example, the flexiblePCB 340 can be connected to the frame front 330 via the flexible PCBadhesive 460. The infrared emitter cover lens 445 can be connected tothe frame back 335 via infrared emitter cover lens adhesive 455. Thecoupling also can be indirect via intervening components.

FIG. 5 illustrates an example of capturing visible light with cameras114A-B. Visible light is captured by the left visible light camera 114Awith a round field of view (FOV). 111A. A chosen rectangular left rawimage 558A is used for image processing by image processor 612 (FIG. 6). Visible light is also captured by the right visible light camera 114Bwith a round FOV 111B. A rectangular right raw image 558B chosen by theimage processor 612 is used for image processing by processor 612. Basedon processing of the left raw image 558A and the right raw image 558Bhaving an overlapping field of view 513, a three-dimensional image 515of a three-dimensional scene, referred to hereafter as an immersiveimage, is generated by processor 612 and displayed by displays 180C and180D and which is viewable by the user.

FIG. 6 illustrates a high-level functional block diagram includingexample electronic components disposed in electronic eyewear device 100or 200. The illustrated electronic components include the processor 632,the memory 634, and the see-through image display 180C and 180D.

Memory 634 includes instructions for execution by processor 632 toimplement the functionality of electronic eyewear devices 100 and 200,including instructions for processor 632 to control the image 515.Processor 632 receives power from battery 650 and executes theinstructions stored in memory 634, or integrated with the processor 632on-chip, to perform the functionality of electronic eyewear devices 100and 200 and to communicate with external devices via wirelessconnections.

The electronic eyewear devices 100 and 200 may incorporate an eyemovement tracker 645 (e.g., shown as infrared emitter 215 and infraredcamera 220 in FIG. 2B) and may provide user interface adjustments via amobile device 690 and a server system 698 connected via variousnetworks. Mobile device 690 may be a smartphone, tablet, laptopcomputer, access point, or any other such device capable of connectingwith the electronic eyewear devices 100 or 200 using both a low-powerwireless connection 625 and a high-speed wireless connection 637. Mobiledevice 690 is further connected to server system 698 via a network 695.The network 695 may include any combination of wired and wirelessconnections.

Electronic eyewear devices 100 and 200 may include at least two visiblelight cameras 114A-B (one associated with the left lateral side 170A andone associated with the right lateral side 170B). Electronic eyeweardevices 100 and 200 further include two see-through image displays180C-D of the optical assembly 180A-B (one associated with the leftlateral side 170A and one associated with the right lateral side 170B).Electronic eyewear devices 100 and 200 also include image display driver642, image processor 612, low-power circuitry 620, and high-speedcircuitry 630. The components shown in FIG. 6 for the electronic eyeweardevices 100 and 200 are located on one or more circuit boards, forexample, a PCB or flexible PCB 140, in the temples. Alternatively, oradditionally, the depicted components can be located in the temples,frames, hinges, hinged arms, or bridge of the electronic eyewear devices100 and 200. Left and right visible light cameras 114A-B can includedigital camera elements such as a complementarymetal-oxide-semiconductor (CMOS) image sensor, charge coupled device, alens, or any other respective visible or light capturing elements thatmay be used to capture data, including images of scenes with unknownobjects.

Eye movement tracking programming 645 implements the user interfacefield of view adjustment instructions, including instructions to causethe electronic eyewear devices 100 or 200 to track, via the eye movementtracker 213, the eye movement of the eye of the user of the electroniceyewear devices 100 or 200. Other implemented instructions (functions)cause the electronic eyewear devices 100 and 200 to determine the FOVadjustment to the initial FOV 111A-B based on the detected eye movementof the user corresponding to a successive eye direction. Furtherimplemented instructions generate a successive displayed image of thesequence of displayed images based on the field of view adjustment. Thesuccessive displayed image is produced as visible output to the user viathe user interface. This visible output appears on the see-through imagedisplays 180C-D of optical assembly 180A-B, which is driven by imagedisplay driver 642 to present the sequence of displayed images,including the initial displayed image with the initial field of view andthe successive displayed image with the successive field of view.

As shown in FIG. 6 , high-speed circuitry 630 includes high-speedprocessor 632, memory 634, and high-speed wireless circuitry 636. In theexample, the image display driver 642 is coupled to the high-speedcircuitry 630 and operated by the high-speed processor 632 in order todrive the left and right image displays 180C-D of the optical assembly180A-B. High-speed processor 632 may be any processor capable ofmanaging high-speed communications and operation of any generalcomputing system needed for electronic eyewear device 100 or 200.High-speed processor 632 includes processing resources needed formanaging high-speed data transfers on high-speed wireless connection 637to a wireless local area network (WLAN) using high-speed wirelesscircuitry 636. In certain examples, the high-speed processor 632executes an operating system such as a LINUX operating system or othersuch operating system of the electronic eyewear device 100 or 200 andthe operating system is stored in memory 634 for execution. In additionto any other responsibilities, the high-speed processor 632 executing asoftware architecture for the electronic eyewear device 100 or 200 isused to manage data transfers with high-speed wireless circuitry 636. Incertain examples, high-speed wireless circuitry 636 is configured toimplement Institute of Electrical and Electronic Engineers (IEEE) 802.11communication standards, also referred to herein as WI-FI®. In otherexamples, other high-speed communications standards may be implementedby high-speed wireless circuitry 636.

Low-power wireless circuitry 624 and the high-speed wireless circuitry636 of the electronic eyewear devices 100 and 200 can include shortrange transceivers (BLUETOOTH®) and wireless wide, local, or wide areanetwork transceivers (e.g., cellular or WI-FI®). Mobile device 690,including the transceivers communicating via the low-power wirelessconnection 625 and high-speed wireless connection 637, may beimplemented using details of the architecture of the electronic eyeweardevice 100 and 200, as can other elements of network 695.

Memory 634 includes any storage device capable of storing various dataand applications, including, among other things, color maps, camera datagenerated by the left and right visible light cameras 114A-B and theimage processor 612, as well as images generated for display by theimage display driver 642 on the see-through image displays 180C-D of theoptical assembly 180A-B. While memory 634 is shown as integrated withhigh-speed circuitry 630, in other examples, memory 634 may be anindependent standalone element of the electronic eyewear device 100 or200. In certain such examples, electrical routing lines may provide aconnection through a system on chip that includes the high-speedprocessor 632 from the image processor 612 or low-power processor 622 tothe memory 634. In other examples, the high-speed processor 632 maymanage addressing of memory 634 such that the low-power processor 622will boot the high-speed processor 632 any time that a read or writeoperation involving memory 634 is needed.

Server system 698 may be one or more computing devices as part of aservice or network computing system, for example, that includes aprocessor, a memory, and network communication interface to communicateover the network 695 with the mobile device 690 and electronic eyeweardevices 100 and 200. Electronic eyewear devices 100 and 200 may beconnected with a host computer. For example, the electronic eyeweardevices 100 or 200 may be paired with the mobile device 690 via thehigh-speed wireless connection 637 or connected to the server system 698via the network 695.

Output components of the electronic eyewear devices 100 and 200 includevisual components, such as the left and right image displays 180C-D ofoptical assembly 180A-B as described in FIGS. 2C-D (e.g., a display suchas a liquid crystal display (LCD), a plasma display panel (PDP), a lightemitting diode (LED) display, a projector, or a waveguide). The imagedisplays 180C-D of the optical assembly 180A-B are driven by the imagedisplay driver 642. The output components of the electronic eyeweardevices 100 and 200 further include acoustic components (e.g.,speakers), haptic components (e.g., a vibratory motor), other signalgenerators, and so forth. The input components of the electronic eyeweardevices 100 and 200, the mobile device 690, and server system 698, mayinclude alphanumeric input components (e.g., a keyboard, a touch screenconfigured to receive alphanumeric input, a photo-optical keyboard, orother alphanumeric input components), point-based input components(e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, orother pointing instruments), tactile input components (e.g., a physicalbutton, a touch screen that provides location and force of touches ortouch gestures, or other tactile input components), audio inputcomponents (e.g., a microphone 130), and the like. The microphone 130may provide voice inputs from the user to the voice command intenthandler software 820 for processing by the high-speed circuitry 630, aswill be described further below with respect to FIG. 8 .

Electronic eyewear devices 100 and 200 may optionally include additionalperipheral device elements such as ambient light and spectral sensors,biometric sensors, heat sensor 640, or other display elements integratedwith electronic eyewear device 100 or 200. For example, the peripheraldevice elements may include any I/O components including outputcomponents, motion components, position components, or any other suchelements described herein. The electronic eyewear devices 100 and 200can take other forms and may incorporate other types of frameworks, forexample, a headgear, a headset, or a helmet.

For example, the biometric components of the electronic eyewear devices100 and 200 may include components to detect expressions (e.g., handexpressions, facial expressions, vocal expressions, body gestures, oreye tracking), measure biosignals (e.g., blood pressure, heart rate,body temperature, perspiration, or brain waves), identify a person(e.g., voice identification, retinal identification, facialidentification, fingerprint identification, or electroencephalogrambased identification), and the like. The motion components includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The position components include location sensor components to generatelocation coordinates (e.g., a Global Positioning System (GPS) receivercomponent), WI-FI® or BLUETOOTH® transceivers to generate positioningsystem coordinates, altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like. Suchpositioning system coordinates can also be received over wirelessconnections 625 and 637 from the mobile device 690 via the low-powerwireless circuitry 624 or high-speed wireless circuitry 636.

Voice-Controlled Settings and Navigation

In sample configurations, the user may propose augmented reality (AR)device settings adjustments and preview the adjustments on-the-go, inany context, without the need to access a paired device. The sampleconfigurations may build upon the infrastructure for supporting voicescans such as “Hey Snapchat, show me some cool space lenses” of the typedescribed in co-pending U.S. Provisional Patent Application Ser. No.63/190,613 filed May 19, 2021, the contents of which are incorporatedherein by reference. Implementation of the sample configurationsdescribed herein may be used to support almost arbitrary voice andnavigation commands such as “set brightness to 10%,” “what's my batterylevel,” or “go to gallery” by decoupling the voice feature from the scanfeature and adding a general-purpose voice command handler that expandsvoice capabilities of the electronic eyewear device 100 or 200. Also,all system settings may be centralized in one place to simplify changesin system settings using simple voice commands.

In conventional portable electronic devices such as electronic eyeweardevices 100 and 200, it is common to require a user to navigate to asystem information section in order to view most settings. Requiringsuch navigation is not very convenient for a quick battery ortemperature level check while using an augmented reality device. Inaddition, changing settings may require access to a paired device, whichshould not be necessary for simple brightness adjustments.

The configurations described herein enable settings to be read andchanged using voice commands and provide an infrastructure for handlingand processing arbitrary voice commands from all contexts and flows ofelectronic eyewear devices 100 and 200. In sample configurations, theresults are communicated without disrupting the current operations ofthe electronic eyewear devices 100 and 200. In the sampleinfrastructure, the voice processing is not bound to any particularfeature or component.

The configurations described herein expand the use of a wake word beyondvoice scan and provide infrastructure for general purpose voice commands(not just for settings). For example, the voice commands may includecommands/actions such as:

-   -   . . . volume/brightness up [+10]    -   . . . volume/brightness down [−10]    -   . . . current brightness/volume    -   . . . set brightness/volume to n %    -   . . . brightness auto    -   . . . battery level    -   . . . temperature        The infrastructure may support virtually any well-defined voice        command, and the results may be communicated as a        notification/alert using the infrastructure. In sample        configurations, the notifications/alerts infrastructure presents        the results asynchronously, without disrupting user flow. As a        result, the notifications/alerts infrastructure may be triggered        from virtually any place in the user flow, which makes voice        commands universally accessible. The voice command user        interface may include conventional features for modifying        settings but may also include additional actions that are        available only via voice, like battery level and temperature.

FIG. 7 illustrates a voice scan architecture 700 of the type describedin co-pending U.S. Provisional Patent Application Ser. No. 63/190,613filed May 19, 2021, where a scan intent handler 710 determines theuser's intent based on at least one of a wake word provided at 720 oreye scan intent data provided at 730. A scan controller 740 may provideany received user audio data to speech-to-text service software 750 totranscribe the user's voice query following the wake word. Thevoice-to-text service software 750 may be provided on the electroniceyewear device 100 or 200 or may be provided in backend servicesavailable on the backend server system 698 accessible to the electroniceyewear device 100 or 200 to transcribe the user's spoken words. Theidentified spoken words may be used as tags (keywords) for lenses orother augmented reality objects to be provided to the display of theelectronic eyewear device 100 in response to the captured voice data or,as described herein, the spoken words may include action keywords thatmay be used to select settings adjustments, navigation, scan, or otheractions to be performed by the electronic eyewear device 100 or 200. Thetranscribed voice query is provided to a voice scan controller 760 todetermine the user's query. In sample configurations, the user's querymay be assumed to be a scan request to view a particular lens availablethrough a voice scan application programming interface 770 or from avoice scan lens storage component 780.

FIG. 8 illustrates a generalized voice command system 800 that modifiesthe voice scan architecture 700 of FIG. 7 to include a voice actionsservice 810 including a voice command intent handler 820 that performsthe initial interpretation of the voice command and routes it to theappropriate controller depending on its nature. In sampleconfigurations, the voice command intent handler 820 may be implementedin software on the electronic eyewear device 100 or 200 as illustratedin FIG. 6 . In the illustrated configuration, a wake word 720 isreceived by the voice command intent handler 820 to begin the process ofdetermining the user's intent for the following voice command. Uponreceipt of the wake word (e.g., “Hey Snapchat,” “Hey Siri,” “Alexa,”etc.), the voice command intent handler 820 provides the received voicedata to the speech-to-text service 750. The recognized text is providedto action detector 830 and the recognized text is compared to a set ofaction keywords identifying the type of action being requested by theuser. For example, the action detector 830 may match the recognized textagainst several regular expressions that are linked to certaincommands/actions such as:

-   -   “Set . . . ”    -   “Reduce . . . ”    -   “Increase . . . ”    -   “Volume . . . ”    -   “Brightness . . . ”    -   “Go to . . . ”    -   “Open . . . ”

etc.

If the recognized phrase is classified as a setting action (e.g., “set,”“reduce,” “increase,” “volume,” “brightness,” etc.), the recognizedphrase will be forwarded by the voice command intent handler to thesettings controller 840 to adjust a setting based on other keywords inthe recognized text. For example, the settings controller 840 may adjusta volume setting, a brightness setting, and the like. On the other hand,if the recognized phrase is classified as a navigation action (e.g., “goto” or “open”), the recognized phrase will be forwarded to thenavigation controller 850 to navigate based on other keywords in therecognized text. Otherwise, the recognized phrase is provided to thescan controller 740 as in the configuration of FIG. 7 to be handled as ascan query. For example, if the user provided the text “Hey Snapchat,please set the brightness to 100 percent,” the voice command intenthandler 820 would recognize the text as a settings action based on theword “set” and provide at least the recognized keywords to the settingscontroller 840 to set the brightness to 100 percent. Similarly, therequest may specify that the brightness be set to a value between 0-9and the like. More generally, the recognized phrase or keywords in therecognized text may be provided to one of a plurality of controllers,where each of the plurality of controllers is associated with adifferent action keyword or set of action keywords to implement acommand/action requested by the action keyword or set of actionkeywords. Also, as illustrated in FIG. 8 , the presentation of theresults of a requested action may be provided to the rendered display at860 without disrupting the current action (e.g., rendering of a lens bya lens app).

It will be appreciated that the functionality shown in FIG. 8 may beimplemented on the electronic eyewear device 100 or 200 described aboveand that the results of the actions may be presented to the imagedisplay 180C-D of the optical assembly of the electronic eyewear device100 or 200. However, in other configurations, the pattern matchingperformed by the voice actions service 810 may be replaced with anatural language understanding (NLU) model that may be implemented onthe electronic eyewear device 100 or 200 or provided on a backend serversystem 698 or mobile device 690 accessed via the high-speed wirelessconnection 637.

FIG. 9 illustrates a sample flow chart 900 of the dispatch function ofthe voice actions service 810. As illustrated, voice data from the useris received from the microphone 130 at 910 and converted to text at 920.If a wake word (e.g., “Hey Snapchat”) is not recognized in the processedtext at 930, the voice actions service 810 awaits further input at 910.However, if the wake word is recognized at 930, the action detector 830searches for a settings action phrase (e.g., “ . . . set . . . to . . .”) at 940. When a settings action phrase is detected at 940, therecognized text is provided to the settings controller 840 to adjust thesettings as requested. If no settings action phrase is detected at 940,the action detector 830 searches for a navigation action phrase (e.g., “. . . go . . . to . . . ”) at 950. When a navigation action phrase isdetected at 950, the recognized text is provided to the navigationcontroller 850 to navigate as requested. When no navigation phrase isdetected at 950, it is assumed that the recognized phrase is to beprovided to the scan controller 740. It will be appreciated that thesesteps may be performed in any order and that additional types of actionphrases may be detected for finer parsing of the received voicecommands. Also, it will be appreciated that the system need only detectcertain action words and keywords in the text and may ignore otherwords. Also, as noted above, more sophisticated machine learning ornatural language understanding (NLU) techniques may be implemented onthe electronic eyewear device 100 or 200 or on backend server system 698for more nuanced discrimination of the voice text.

FIGS. 10A-10D illustrate sample user interfaces for what would bepresented to each eye in a sample configuration.

FIG. 10A illustrates the user interface 1000 before an application hasbeen selected. The user is encouraged to provide a voice command and asample command may be suggested. A microphone may be displayed to showthat the device is listening and the user's words optionally may bedisplayed as the words are recognized. The voice-to-text may be alignedat the bottom of the display and presented to the user as the text isrecognized. The text also may be italicized to differentiate from anytext presented by the app. The voice-to-text may fill from right to leftand, if there is a lot of text, the text may appear to move up. Themicrophone and text may be presented as overlays on the user interfaceor as animations.

In FIG. 10B, the user has selected a lens application that is presentedon the user interface as a lens carousel at 1010. In FIG. 10B, the userhas also asked to see the volume level, which is shown as 70% at 1020. Asettings icon 1030 may also be presented to show that the voicecommand/action has been recognized as a settings action. The settingsicon 1030 and the volume data 1020 may be presented as an overlay on theuser interface or may be shown as words (e.g., “volume”) or dataincorporated into the display without disrupting the flow of the user'sinteraction with the lens carousel 1010 or any other aspect of thedisplay by the lens application.

In FIG. 10C, the user has asked to increase the volume by 10%, and thevolume level is updated to 80% at 1040. The display may also indicatethat the volume has been increased by 10%.

In FIG. 10D, a new lens application is presented as a lens carousel onthe user interface at 1050. In FIG. 10D, the user has asked to see thebrightness level, which is shown at 1060 to be 5%. As in FIG. 10B, thesettings icon 1030 and the brightness data 1060 may be presented as anoverlay on the user interface or may be shown as words (e.g.,“brightness”) or data incorporated into the display without disruptingthe flow of the user's interaction with the lens carousel 1050 or anyother aspect of the display by the lens application.

It will be appreciated that the settings and navigation information isdesirably presented on the user interface in a manner that does notinterfere with the underlying application (e.g., lens application). Itwill be further appreciated that the settings and navigation informationmay be presented as numbers, words, icons, animations, or a combinationthereof.

Those skilled in the art will further appreciate that latency may befurther reduced by starting the requested settings adjustments andnavigation without waiting for the full sentence to be completed by theuser. The key words may be recognized as they are spoken and theappropriate actions taken. Also, the commands/actions may be predictedbased on the user's patterns of usage whereby the commands/actions maybe recognized even before they are completed by the user. Thecorresponding notification may be presented to the user so that the usercan verify whether the correct command/action has been applied. Forexample, the display in FIG. 10C could be modified to say “volumeincreased 10%” to provide feedback to the user. This way, the volumecould be adjusted right away and further adjusted by the user if thenotification does not reflect the user's intent. Other suchmodifications will become apparent to those skilled in the art.

Centralizing Settings Management

In the case of portable electronic devices such as electronic eyeweardevices, the various settings may be scattered across the codebase. Forexample, some of the settings may be stored in the SystemInfoService,while others, like Volume and Brightness, may be handled in a connectorservice. These services may require connection to an app on a pairedmobile device and may only be modified after pairing with the mobiledevice and adjusting the values with the paired app over a wirelessconnection. In order to avoid duplication of settings or dependence uponapps and services that increase latency and complexity, it is desirableto centralize settings management into a single place. The dispatchservice described above enables all device settings to be groupedtogether on the portable electronic device for access by the settingscontroller in response to voice commands. Such device settings mayinclude not just the settings that are controlled using remote procedurecalls. Since the device settings may all be accessed on the portableelectronic device, latency may be reduced. Also, since the devicesettings all may be provided on the portable electronic device, they maybe accessed by a swipe, a voice command, a gesture, or another selectionaction.

System Configuration

Techniques described herein may be used with one or more of the computersystems described herein or with one or more other systems. For example,the various procedures described herein may be implemented with hardwareor software, or a combination of both. For example, at least one of theprocessor, memory, storage, output device(s), input device(s), orcommunication connections discussed below can each be at least a portionof one or more hardware components. Dedicated hardware logic componentscan be constructed to implement at least a portion of one or more of thetechniques described herein. For example, and without limitation, suchhardware logic components may include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc. Applications that may includethe apparatus and systems of various aspects can broadly include avariety of electronic and computer systems. Techniques may beimplemented using two or more specific interconnected hardware modulesor devices with related control and data signals that can becommunicated between and through the modules, or as portions of anapplication-specific integrated circuit. Additionally, the techniquesdescribed herein may be implemented by software programs executable by acomputer system. As an example, implementations can include distributedprocessing, component/object distributed processing, and parallelprocessing. Moreover, virtual computer system processing can beconstructed to implement one or more of the techniques or functionality,as described herein.

By way of example, FIG. 11 illustrates a sample configuration of acomputer system 1100 adapted to implement the backend services (e.g.,voice-to-text or image processing services) in accordance with thesystems and methods described herein. In particular, FIG. 11 illustratesa block diagram of an example of a machine 1100 upon which one or moreconfigurations may be implemented. In alternative configurations, themachine 1100 may operate as a standalone device or may be connected(e.g., networked) to other machines. In a networked deployment, themachine 1100 may operate in the capacity of a server machine, a clientmachine, or both in server-client network environments. In an example,the machine 1100 may act as a peer machine in peer-to-peer (P2P) (orother distributed) network environment. In sample configurations, themachine 1100 may be a personal computer (PC), a tablet PC, a set-top box(STB), a personal digital assistant (PDA), a mobile telephone, a smartphone, a web appliance, a server, a network router, switch or bridge, orany machine capable of executing instructions (sequential or otherwise)that specify actions to be taken by that machine. For example, machine1100 may serve as a workstation, a front-end server, or a back-endserver of a communication system. Machine 1100 may implement the methodsdescribed herein by running the software used to implement the botsgenerated as described herein. Further, while only a single machine 1100is illustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein, such as cloud computing, software as aservice (SaaS), other computer cluster configurations.

Examples, as described herein, may include, or may operate on,processors, logic, or a number of components, modules, or mechanisms(herein “modules”). Modules are tangible entities (e.g., hardware)capable of performing specified operations and may be configured orarranged in a certain manner. In an example, circuits may be arranged(e.g., internally or with respect to external entities such as othercircuits) in a specified manner as a module. In an example, the whole orpart of one or more computer systems (e.g., a standalone, client orserver computer system) or one or more hardware processors may beconfigured by firmware or software (e.g., instructions, an applicationportion, or an application) as a module that operates to performspecified operations. In an example, the software may reside on amachine readable medium. The software, when executed by the underlyinghardware of the module, causes the hardware to perform the specifiedoperations.

Accordingly, the term “module” is understood to encompass at least oneof a tangible hardware or software entity, be that an entity that isphysically constructed, specifically configured (e.g., hardwired), ortemporarily (e.g., transitorily) configured (e.g., programmed) tooperate in a specified manner or to perform part or all of any operationdescribed herein. Considering examples in which modules are temporarilyconfigured, each of the modules need not be instantiated at any onemoment in time. For example, where the modules comprise ageneral-purpose hardware processor configured using software, thegeneral-purpose hardware processor may be configured as respectivedifferent modules at different times. Software may accordingly configurea hardware processor, for example, to constitute a particular module atone instance of time and to constitute a different module at a differentinstance of time.

Machine (e.g., computer system) 1100 may include a hardware processor1102 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 1104 and a static memory 1106, some or all of which maycommunicate with each other via an interlink (e.g., bus) 1108. Themachine 1100 may further include a display unit 1110 (shown as a videodisplay), an alphanumeric input device 1112 (e.g., a keyboard), and auser interface (UI) navigation device 1114 (e.g., a mouse). In anexample, the display unit 1110, input device 1112 and UI navigationdevice 1114 may be a touch screen display. The machine 1100 mayadditionally include a mass storage device (e.g., drive unit) 1116, asignal generation device 1118 (e.g., a speaker), a network interfacedevice 1120, and one or more sensors 1122. Example sensors 1122 includeone or more of a global positioning system (GPS) sensor, compass,accelerometer, temperature, light, camera, video camera, sensors ofphysical states or positions, pressure sensors, fingerprint sensors,retina scanners, or other sensors. The machine 1100 may include anoutput controller 1124, such as a serial (e.g., universal serial bus(USB), parallel, or other wired or wireless (e.g., infrared(IR), nearfield communication (NFC), etc.) connection to communicate or controlone or more peripheral devices (e.g., a printer, card reader, etc.).

The mass storage device 1116 may include a machine readable medium 1126on which is stored one or more sets of data structures or instructions1128 (e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 1128 may alsoreside, completely or at least partially, within the main memory 1104,within static memory 1106, or within the hardware processor 1102 duringexecution thereof by the machine 1100. In an example, one or anycombination of the hardware processor 1102, the main memory 1104, thestatic memory 1106, or the mass storage device 1116 may constitutemachine readable media.

While the machine readable medium 1126 is illustrated as a singlemedium, the term “machine readable medium” may include a single mediumor multiple media (e.g., at least one of a centralized or distributeddatabase, or associated caches and servers) configured to store the oneor more instructions 1128. The term “machine readable medium” mayinclude any medium that is capable of storing, encoding, or carryinginstructions for execution by the machine 1100 and that cause themachine 1100 to perform any one or more of the techniques of the presentdisclosure, or that is capable of storing, encoding, or carrying datastructures used by or associated with such instructions. Non-limitingmachine readable medium examples may include solid-state memories, andoptical and magnetic media. Specific examples of machine readable mediamay include non-volatile memory, such as semiconductor memory devices(e.g., Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; Random Access Memory (RAM); Solid StateDrives (SSD); and CD-ROM and DVD-ROM disks. In some examples, machinereadable media may include non-transitory machine-readable media. Insome examples, machine readable media may include machine readable mediathat is not a transitory propagating signal.

The instructions 1128 may further be transmitted or received overcommunications network 1132 using a transmission medium via the networkinterface device 1120. The machine 1100 may communicate with one or moreother machines utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®), IEEE 802.15.4 family ofstandards, a Long Term Evolution (LTE) family of standards, a UniversalMobile Telecommunications System (UMTS) family of standards,peer-to-peer (P2P) networks, among others. In an example, the networkinterface device 1120 may include one or more physical jacks (e.g.,Ethernet, coaxial, or phone jacks) or one or more antennas 1130 toconnect to the communications network 1132. In an example, the networkinterface device 1120 may include a plurality of antennas 1130 towirelessly communicate using at least one of single-inputmultiple-output (SIMO), multiple-input multiple-output (MIMO), ormultiple-input single-output (MISO) techniques. In some examples, thenetwork interface device 1120 may wirelessly communicate using MultipleUser MIMO techniques.

The features and flow charts described herein can be embodied in one ormore methods as method steps or in one or more applications as describedpreviously. According to some configurations, an “application” or“applications” are program(s) that execute functions defined in theprograms. Various programming languages can be employed to generate oneor more of the applications, structured in a variety of manners, such asobject-oriented programming languages (e.g., Objective-C, Java, or C++)or procedural programming languages (e.g., C or assembly language). In aspecific example, a third party application (e.g., an applicationdeveloped using the ANDROID™ or IOS™ software development kit (SDK) byan entity other than the vendor of the particular platform) may bemobile software running on a mobile operating system such as IOS™,ANDROID™, WINDOWS® Phone, or another mobile operating systems. In thisexample, the third party application can invoke API calls provided bythe operating system to facilitate functionality described herein. Theapplications can be stored in any type of computer readable medium orcomputer storage device and be executed by one or more general purposecomputers. In addition, the methods and processes disclosed herein canalternatively be embodied in specialized computer hardware or anapplication specific integrated circuit (ASIC), field programmable gatearray (FPGA) or a complex programmable logic device (CPLD).

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of at least one ofexecutable code or associated data that is carried on or embodied in atype of machine readable medium. For example, programming code couldinclude code for the touch sensor or other functions described herein.“Storage” type media include any or all of the tangible memory of thecomputers, processors or the like, or associated modules thereof, suchas various semiconductor memories, tape drives, disk drives and thelike, which may provide non-transitory storage at any time for thesoftware programming. All or portions of the software may at times becommunicated through the Internet or various other telecommunicationnetworks. Such communications, for example, may enable loading of thesoftware from one computer or processor into another, for example, fromthe server system 720 or host computer of the service provider into thecomputer platforms of the client devices 810. Thus, another type ofmedia that may bear the programming, media content or meta-data filesincludes optical, electrical, and electromagnetic waves, such as usedacross physical interfaces between local devices, through wired andoptical landline networks and over various air-links. The physicalelements that carry such waves, such as wired or wireless links, opticallinks, or the like, also may be considered as media bearing thesoftware. As used herein, unless restricted to “non-transitory”,“tangible”, or “storage” media, terms such as computer or machine“readable medium” refer to any medium that participates in providinginstructions or data to a processor for execution.

Hence, a machine readable medium may take many forms of tangible storagemedium. Non-volatile storage media include, for example, optical ormagnetic disks, such as any of the storage devices in any computer(s) orthe like, such as may be used to implement the client device, mediagateway, transcoder, etc. shown in the drawings. Volatile storage mediainclude dynamic memory, such as main memory of such a computer platform.Tangible transmission media include coaxial cables; copper wire andfiber optics, including the wires that comprise a bus within a computersystem. Carrier-wave transmission media may take the form of electric orelectromagnetic signals, or acoustic or light waves such as thosegenerated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer may read at least one of programmingcode or data. Many of these forms of computer readable media may beinvolved in carrying one or more sequences of one or more instructionsto a processor for execution.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”“includes,” “including,” or any other variation thereof, are intended tocover a non-exclusive inclusion, such that a process, method, article,or apparatus that comprises or includes a list of elements or steps doesnot include only those elements or steps but may include other elementsor steps not expressly listed or inherent to such process, method,article, or apparatus. An element preceded by “a” or “an” does not,without further constraints, preclude the existence of additionalidentical elements in the process, method, article, or apparatus thatcomprises the element.

Unless otherwise stated, any and all measurements, values, ratings,positions, magnitudes, sizes, and other specifications that are setforth in this specification, including in the claims that follow, areapproximate, not exact. Such amounts are intended to have a reasonablerange that is consistent with the functions to which they relate andwith what is customary in the art to which they pertain. For example,unless expressly stated otherwise, a parameter value or the like mayvary by as much as ±10% from the stated amount.

In addition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in various examples for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, the subject matter to be protected liesin less than all features of any single disclosed example. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separately claimed subjectmatter.

While the foregoing has described what are considered to be the bestmode and other examples, it is understood that various modifications maybe made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that they may be appliedin numerous applications, only some of which have been described herein.It is intended by the following claims to claim any and allmodifications and variations that fall within the true scope of thepresent concepts.

What is claimed is:
 1. An electronic eyewear device adapted to be wornon a head of a user, comprising: a microphone; a memory that storesinstructions; and a processor that executes the instructions to performoperations including: receiving audio data from the microphone;processing the audio data to identify a wake word; identifying at leastone action keyword in the audio data; and upon identification of thewake word, providing the audio data to a settings controller to adjustsettings of the electronic eyewear device as specified by the audio datawhen the at least one action keyword is indicative of a request toadjust a setting of the electronic eyewear device or to a navigationcontroller to navigate to system information of the electronic eyeweardevice as specified by the audio data when the at least one actionkeyword is indicative of a request to navigate to the system informationof the electronic eyewear device.
 2. The electronic eyewear device ofclaim 1, wherein the processor executes the instructions to performadditional operations including providing the audio data to a scancontroller when the audio data does not contain an action keywordindicative of a request to adjust a setting of the electronic eyeweardevice or of a request to navigate to system information of theelectronic eyewear device.
 3. The electronic eyewear device of claim 1,further comprising voice-to-text software that is executed by theprocessor to convert the audio data to text.
 4. The electronic eyeweardevice of claim 1, further comprising voice command intent handlersoftware that is executed by the processor to identify action keywordsin the audio data and to provide the identified action keywords to theappropriate controller based on which action keyword or set of actionkeywords are identified in the audio data.
 5. The electronic eyeweardevice of claim 4, wherein the voice command intent handler softwarecomprises a natural language understanding (NLU) model.
 6. Theelectronic eyewear device of claim 1, further comprising a display,wherein the processor executes the instructions to perform additionaloperations including presenting results of an action requested by the atleast one action keyword or set of action keywords to the displaywithout disrupting a current action being presented to the display aspart of execution of a software application.
 7. The electronic eyeweardevice of claim 6, wherein the processor executes the instructions toperform additional operations including presenting a notification on thedisplay indicating an action taken in response to the audio datareceived at the microphone.
 8. A method of controlling an electroniceyewear device, comprising: receiving audio data from a microphone;processing the audio data to identify a wake word; identifying at leastone action keyword in the audio data; and upon identification of thewake word, providing the audio data to a settings controller to adjustsettings of the electronic eyewear device as specified by the audio datawhen the at least one action keyword is indicative of a request toadjust a setting of the electronic eyewear device or to a navigationcontroller to navigate to system information of the electronic eyeweardevice as specified by the audio data when the at least one actionkeyword is indicative of a request to navigate to the system informationof the electronic eyewear device.
 9. The method of claim 8, furthercomprising providing the audio data to a scan controller when the audiodata does not contain an action keyword indicative of a request toadjust a setting of the electronic eyewear device or of a request tonavigate to system information of the electronic eyewear device.
 10. Themethod of claim 8, further comprising executing voice command intenthandler software to identify the action keywords in the audio data andto provide the identified action keywords to an appropriate controllerbased on which action keyword or set of action keywords are identifiedin the audio data.
 11. The method of claim 10, wherein executing thevoice command intent handler software comprises implementing a naturallanguage understanding (NLU) model.
 12. The method of claim 8, furthercomprising presenting results of an action requested by the at least oneaction keyword or set of action keywords to a display without disruptinga current action being presented to the display as part of execution ofa software application.
 13. The method of claim 12, further comprisingpresenting a notification on the display indicating an action taken inresponse to the audio data received at the microphone.
 14. Anon-transitory computer-readable storage medium that stores instructionsthat when executed by at least one processor cause the at least oneprocessor to control an electronic eyewear device by performingoperations including: receiving audio data from a microphone; processingthe audio data to identify a wake word; identifying at least one actionkeyword in the audio data; and upon identification of the wake word,providing the audio data to a settings controller to adjust settings ofthe electronic eyewear device as specified by the audio data when the atleast one action keyword is indicative of a request to adjust a settingof the electronic eyewear device or to a navigation controller tonavigate to system information of the electronic eyewear device asspecified by the audio data when the at least one action keyword isindicative of a request to navigate to the system information of theelectronic eyewear device.
 15. The medium of claim 14, furthercomprising instructions that when executed by the at least one processorcauses the at least one processor to provide the audio data to a scancontroller when the audio data does not contain an action keywordindicative of a request to adjust a setting of the electronic eyeweardevice or of a request to navigate to system information of theelectronic eyewear device.
 16. The medium of claim 14, furthercomprising instructions that when executed by the at least one processorcauses the at least one processor to at least one of (1) present resultsof an action requested by the at least one action keyword or set ofaction keywords to a display without disrupting a current action beingpresented to the display as part of execution of a software applicationor (2) present a notification on the display indicating an action takenin response to the audio data received at the microphone.